Skip to content

Username dots path traversal - #1634

Open
vmo69 wants to merge 2 commits into
dovecot:mainfrom
vmo69:username_dots_path_traversal
Open

Username dots path traversal#1634
vmo69 wants to merge 2 commits into
dovecot:mainfrom
vmo69:username_dots_path_traversal

Conversation

@vmo69

@vmo69 vmo69 commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

DOV-9793

@vmo69
vmo69 force-pushed the username_dots_path_traversal branch from 797f74e to b4a9978 Compare September 10, 2026 10:49
Comment thread data/settings.js
databases.

If you want to allow all characters, leave the value empty.`
If you want to allow all characters, leave the value empty.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Duplicate heading. 2.4-to-2.4.x.md already has ### v2.4.5 to v2.4.6 above the four existing
    2.4.6 includes. New include must go under it, not new heading.

  2. data/updates.js not touched. Convention: add keys (e.g. auth_username_dots_rejected:
    '2.4.6', settings_mail_path_confined: '2.4.6') and use changed: { key: ... } blocks on
    auth_username_chars, mail_home, mail_path, index/cache/control/alt paths instead of plain text
    appends.

  3. documentation-pro: no branch. Needs data/updates.js (3.3.0), settings.js changes.

  4. Wording nits in 2.4.6-path-traversal.inc

  • "never valid RFC 5322 addresses": usernames need not be addresses. Say "cannot exist as
    directory names".
  • Add: templates starting with ~/ or %{home} have no literal prefix and are only normalized.
  • If finding 1 (in core MR) stays as is, state that an empty trailing variable is rejected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants